Method and system for audio/video bridging aware shortest path bridging

ABSTRACT

Aspects of a method and system for Audio/Video Bridging aware shortest path bridging are provided. In this regard, network nodes which are AVB enabled and capable of routing information based on a desired path cost and/or a desired quality of service (QoS) may be identified, and an AVB enabled path comprising one or more of the identified nodes may be established for communication over a network. In this regard, the desired cost may be a least cost and may be the “shortest path” between two nodes in a network. Additionally, the nodes maybe identified using Shortest path Bridging protocols and/or Audio Video Bridging protocols and/or extensions thereof. Also, bridge protocol data units may be exchanged to identify the nodes.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application makes reference to, claims priority to and claims benefit from U.S. Provisional Patent Application Ser. No. 60/917,870 filed on May 14, 2007.

The above stated provisional application is hereby incorporated herein by reference in its entirety.

FIELD OF THE INVENTION

Certain embodiments of the invention relate to networking. More specifically, certain embodiments of the invention relate to a method and system for Audio/Video Bridging Aware shortest path bridging.

BACKGROUND OF THE INVENTION

An increasing amount of data, and in particular multimedia content, transmitted over networks has led to much research into ways to improve the quality and reliability of streaming data over bridged local area networks. Accordingly, the IEEE is in the process of standardizing a suite of protocols collectively known as Audio Video Bridging and extensions thereto (collectively referred to herein as AVB). The individual protocols include, among others, IEEE P802.1AS—IEEE Standard for Local and Metropolitan Area Networks—Timing and Synchronization for Time-Sensitive Applications in Bridged Local Area Networks, IEEE P801.1Qat—IEEE Standard for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks—Amendment 9: Stream Reservation Protocol (SRP) and IEEE P802.1Qav: IEEE Standard for Local and Metropolitan Area Networks: Virtual Bridged Local Area Networks—Amendment 11: Forwarding and Queuing for Time-Sensitive Streams.

Applications of Audio/Video Bridging protocols include streaming compressed and/or uncompressed Audio and/or Video between various pieces of equipment. An exemplary transmission may comprise streaming uncompressed audio from an Audio/Video receiver to multiple Networked Speakers over an Ethernet network. In this regard, it may be necessary that the rendering of Audio in all speakers is synchronized so as not to affect the listener's experience. In this manner, the audio video bridging protocols are likely to be deployed in situations where quality of service is paramount to the user experience.

Another protocol being developed to improve network communications is IEEE 802.1aq—Shortest Path Bridging (SPB). In this regard, Shortest Path Bridging, may be utilized to determine least cost paths across a network while eliminating redundant paths or loops. In this regard, redundant paths may cause routing tables to fail since one address may be seen at multiple ports. Additionally, redundant paths may result in broadcast storms, where packets are forwarded in an endless loop, consuming processing resources and bandwidth.

Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.

BRIEF SUMMARY OF THE INVENTION

A system and/or method is provided for Audio/Video Bridging aware shortest path bridging, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.

These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1A is a block diagram illustrating exemplary AVB enabled Audio/Video equipment that may transmit and/or receive data over a network, in connection with an embodiment of the invention.

FIG. 1B is a diagram illustrating principles of shortest path bridging, in connection with an embodiment of the invention.

FIG. 2 is a diagram of an exemplary network comprising AVB enabled and non-AVB enabled nodes, in accordance with an embodiment of the invention.

FIG. 3 is a flow chart illustrating exemplary paths for determining a least cost AVB enabled path across a network, in accordance with an embodiment of the invention.

FIG. 4 is a flow chart illustrating transmission of an AVB data stream utilizing AVB aware Shortest Path Bridging, in accordance with an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Certain embodiments of the invention may be found in a method and system for Audio/Video Bridging aware shortest path bridging. In this regard, network nodes, which are AVB enabled and capable of routing information based on a desired path cost and/or a desired quality of service (QoS), may be identified. Furthermore, an AVB enabled path comprising one or more of the identified nodes may be established for communication over a network. In this regard, the desired cost may be a least cost and may be a “shortest path” between two nodes in a network. Additionally, the nodes may be identified using Shortest Path Bridging protocols and/or Audio Video Bridging protocols and/or extensions thereof. Also, bridge protocol data units may be exchanged to identify the nodes, and may comprise one or more bits capable of identifying nodes which are AVB enabled and capable of routing information based on a desired path cost and/or quality of service. Aspects of the invention may enable network nodes to determine the availability of resources which may be reserved in one or more other nodes. Also, network traffic handled by one or more nodes which are AVB enabled and capable of routing information based on a desired path cost and/or a desired (QoS) may be monitored to enable identifying other nodes which are AVB enabled and capable of routing information based on a desired path cost and/or a desired (QoS). In this regard, SRP registration and or SRP reservation packets may be monitored to identify nodes which are AVB enabled and capable of routing information based on a desired path cost and/or a desired (QoS). Additionally, aspects of the invention may enable storage of a table, database, or other data structure which may enable indicating which nodes in a network may be AVB enabled.

FIG. 1 is a block diagram illustrating exemplary AVB enabled Audio/Video equipment that may transmit and/or receive data over a network, in accordance with an embodiment of the invention. Referring to FIG. 1, there is shown AVB enabled Audio/Video equipment 100 that comprises a host 106a and a network interface hardware (NIHW) device 114. The NIHW device 114 may further comprise a medium access control (MAC) controller 108a and a transceiver 104, to enable communication over a network. In various embodiments of the invention, the network may, for example, utilize Ethernet technology and may communicate over one or more twisted pair channels or a wireless channel. In various embodiments of the invention, the AVB enabled A/V equipment may comprise, for example, a microphone, an instrument, a sound board, a sound card, a video camera, a media player, a graphics card, or other audio and/or video device.

The transceiver 110 may comprise suitable logic, circuitry, and/or code that may enable communication, for example, transmission and reception of data, between the AVB enabled Audio/Video equipment 100 and a network. The transceiver 110 a may support, for example, Ethernet operations. The transceiver 110 a may enable multi-rate communications, such as 10 Mbps, 100 Mbps, 1000 Mbps (or 1 Gbps) and/or 10 Gbps, for example. In this regard, the transceiver 110 may support standard-based data rates and/or non-standard data rates. Moreover, the transceiver 110 a may support standard Ethernet link lengths or ranges of operation and/or extended ranges of operation.

The transceiver 110 may be configured to handle all the physical layer requirements, which include, but are not limited to, packetization, data transfer and serialization/deserialization (SERDES), in instances where such an operation is required. Additionally, in order to support AVB protocols, the transceiver 110 may be enabled to generate timestamps corresponding to the transmission and/or reception of data. Data packets received by the transceiver 110 a from the MAC controller 108 a may include data and header information for each of the above six functional layers. The transceiver 110 may be configured to encode data packets that are to be transmitted over a network and/or to decode data packets received from a network.

The data transmitted and/or received by the transceiver 110 a may be formatted in accordance with the well-known OSI protocol standard. The OSI model partitions operability and functionality into seven distinct and hierarchical layers. Generally, each layer in the OSI model is structured so that it may provide a service to the immediately higher interfacing layer. For example, layer 1, or physical (PHY) layer, may provide services to layer 2 and layer 2 may provide services to layer 3. The data transmitted may comprise frames of Ethernet media independent interface (MII) data which may be delimited by start of stream and end of stream delimiters, for example.

The host 106 may represent layer 3 and above, the MAC controller 108 may represent layer 2 and above and the transceiver 110 may represent the operability and/or functionality of layer 1 or the PHY layer. In this regard, the transceiver 110 a may be referred to as a PHY device or a PHY transceiver, for example. The host 106 a may comprise suitable logic, circuitry, and/or code that may enable operability and/or functionality of the five highest functional layers for data packets that are to be transmitted over a network. Since each layer in the OSI model provides a service to the immediately higher interfacing layer, the MAC controller 108 may provide the necessary services to the host 106 a to ensure that packets are suitably formatted and communicated to the transceiver 110. During transmission, each layer adds its own header to the data passed on from the interfacing layer above it. During reception, a compatible device having a similar OSI stack strips off the headers as the message passes from the lower layers up to the higher layers.

The MAC controller 108 may comprise suitable logic, circuitry, and/or code that may enable handling of data link layer, layer 2, operability and/or functionality in the AVB enabled Audio/Video equipment 100. Accordingly, the MAC controller 108 may be configured to implement Ethernet protocols, such as those based on the IEEE 802.3 standard, for example. Similarly, the MAC controller 108 may be enabled to implement AVB protocols such as IEEE 801.1Qat and IEEE 802.1Qav. Additionally, the MAC controller 108 may be enabled to communicate the AVB compatibility of the AVB enabled equipment 100. In this regard, the MAC controller may support the discovery of network paths that are AVB enabled.

The MAC controller 108 may communicate with the transceiver 110 a via an interface 118 and with the host 106 via a bus controller interface 116. The interface 118 may correspond to an Ethernet interface that comprises protocol and/or link management control signals. The interface 118 may be a multi-rate interface and/or media independent interface (MII). The bus controller interface 116 a may correspond to a PCI or PCI-X interface. Notwithstanding, the invention is not limited in this regard.

In operation, a first AVB enabled equipment may communicate with a second AVB enabled equipment across a network. Accordingly, aspects of the invention may enable determining a least cost AVB enabled path between the two AVB enabled equipments. In this regard, the AVB enabled equipments and any intermediary nodes comprising the network, may be similar to the AVB enabled equipment 100.

FIG. 1B is a diagram illustrating principles of shortest path bridging, in connection with an embodiment of the invention. Referring to FIG. 1B there is shown a network 150 comprising 4 network nodes 152, 154, 156, and 158, and 4 network links 160, 162, 164, 166.

The network links 160, 162, 164, and 166 may comprise physical channels for conveying information in the network 150. In this regard, the links may, for example, comprise twisted pair cabling, coaxial cabling, fiber optic cabling, and/or wireless channels. In the embodiment of the invention depicted in FIG. 1B, the links 160 and 162 may have a link cost of 1, whereas the links 164 and 166 may have a link cost of 2. In this regard, the link cost may be associated with the technology, speed, bandwidth, bit error rate, packet error rate, or other characteristics of the links. Accordingly, lower link cost may, for example, translate to faster and/or more efficient communication of data.

The nodes 152, 154, 156, and 158 may comprise suitable logic circuitry, and/or code that may enable transmission and/or reception of data via a network. In this regard, the nodes may each comprise multiple ports for sending/receiving data, such as the ports A and B illustrated in the FIG. 1B. The nodes 152, 154, 156, and 158 may be enabled to determine paths across a network for routing the data. Accordingly, the nodes 152, 154, 156, and 158 may be enabled to implement algorithms and/or protocols for determining network topology such as 802.1aq Shortest Path Bridging (SPB) and other related protocols and/or algorithms such as Spanning Tree Protocol (STP), IEEE 802.1w Rapid Spanning Tree Protocol (RSTP), and IEEE 802.1s Multiple Spanning Tree Protocol (MSTP). Additionally, the nodes 152 nodes 152, 154, 156, and 158 may comprise one or more routing tables or other databases which may enable storing port configurations, AVB compatibility information of nodes comprising the network 150, and/or other information associated with parsing, routing, and /or otherwise processing of network traffic.

In operation, the nodes 152, 154, 156, and 158 may, for example, utilize SPB to discover an optimum path across the network 150. In this regard, the nodes 152, 154, 156, and 158 may exchange bridge protocol data units to discover the topology of the network 150. In this manner, the nodes may discover that there is more than one path between the node 152 and 156. Accordingly, one or more of the nodes may block a port in order to break the loop caused by the parallel paths. Additionally, when configuring ports, SPB may enable determining link costs across then network and may thus enable configuring ports to provide an optimum path in each direction between the nodes 152 and 158. For example, the node 152 may block port B to incoming traffic from the node 158 and the node 152 may block port B to incoming traffic from the node 152. Thus, traffic in both directions between the node 152 and 158 may be conveyed along the optimal path comprising the links 160 and 162. Also, in various embodiments of the invention, a cost associated with one or more of the links 160, 162, 164, and 166 may vary dynamically. Accordingly, the nodes 152, 154, 156, 158 may be enabled to detect changes in network link costs and may accordingly dynamically reconfigure one or more network ports to maintain a particular cost or range of cost. In this regard, one or more routing tables and/or databases may be periodically updated.

FIG. 2 is a diagram of an exemplary network comprising AVB enabled and non-AVB enabled nodes, in accordance with an embodiment of the invention. Referring to FIG. 2 there is shown two end systems 202 a and 202 b, a plurality of AVB enabled nodes 208, and a non-AVB enabled node 210.

The end systems 202 a and 202 b may comprise suitable logic, circuitry, and/or code that may enable transmitting and/or receiving data over a network utilizing AVB protocols. In this regard, the end systems 202 a and 202 b may be similar to or the same as the AVB enabled audio/video equipment 100 of FIG. 1.

The AVB enabled nodes 208 may comprise suitable logic, circuitry, and/or code that may enable transmitting and/or receiving data over a network utilizing AVB protocols. In this regard, the AVB enabled nodes 208 may be similar to or the same as the AVB enabled audio/video equipment 100 of FIG. 1.

The non-AVB enabled node 210 may comprise suitable logic, circuitry, and/or code that may enable transmitting and/or receiving data over a network. In this regard, the non-AVB enabled nodes 208 may be a conventionally network node, such as a bridge, switch, or router. In various instances, the non-AVB enabled node 210 may be similar to the nodes 208 but may have AVB networking disabled via, for example, software or firmware configuration.

The network path 206 may comprise the least cost path between the end systems 202 a and 202 b. In this regard, the path 206 may be an optimal network path for non-AVB traffic between the end systems 202 a and 202 b.

The network path 204 may comprise the least cost AVB enabled path between the end systems 202 a and 202 b. In this regard, the path 206 may be an optimal network path for AVB traffic between the end systems 202 a and 202 b.

In various embodiments of the invention, AVB compatibility may be factored into link cost. For example, by assigning non-AVB links a higher link cost, aspects of the invention may enable setting a preference for AVB enabled paths.

In the network 200, each of the end systems 202 and the nodes 208 and 210, may be enabled to discover the topology of the network 200. In this regard, the protocol may enable discovering a least cost path between two nodes and/or a least cost AVB enabled path between two nodes. To determine or learn AVB compatibility of network nodes, the AVB traffic may be monitored. In one example, the nodes 208 and the end systems 202 may identify AVB traffic and parse the source address of the traffic to identify AVB enabled nodes. In another example, SRP registration and/or reservation packets may be monitored and/or processed to identify AVB enabled nodes. Additionally, to determine or discover the topology of the network 200, Bridge Protocol Data Units (BPDU) may be exchanged by the nodes 208 and 210. In one embodiment of the invention, the BPDU's may be modified to comprise AVB compatibility information for a node. In another embodiment of the invention, BPDUs may be followed and/or preceded by other control packets which convey AVB compatibility for a node. Accordingly, one or more routing tables and/or other databases may be created and/or updated based on received AVB traffic and/or received BPDUs.

In an exemplary operation, the end system 202 b may request a video stream from the end system 202 a. Accordingly, network resources may be reserved over the path 204 to provide a guaranteed quality of service for the video stream. Conversely, the end system 202 b may transmit general traffic, an email or web traffic for example, via the path 206. Accordingly, general traffic may experience minimal delays and/or latencies while AVB traffic may be provided guaranteed resources across a network.

FIG. 3 is a flow chart illustrating exemplary steps for determining a least cost AVB enabled path across a network, in accordance with an embodiment of the invention. Referring to FIG. 3, the exemplary steps may begin with step 302 when one or more network nodes attempt to discover the topology of a network to which they are connected. Subsequent to step 302, the exemplary steps may advance to step 304. In step 304, the one or more nodes may utilize SPB protocols to discover the network topology. However, in addition to standard SPB information exchanges, nodes comprising the network may additionally communicate whether they are AVB enabled. Subsequent to step 304, the exemplary steps may advance to step 306. In step 306, a network node may gather received information pertaining to link costs across various paths in the network. Accordingly, the paths may be sorted according to link cost or available quality of service. Subsequent to step 306, the exemplary steps may advance to step 308. In step 308, it may be determined which of the paths are AVB enabled. Accordingly, a least cost path overall may be determined and a least cost AVB enabled path may be determined. In various instances, the least cost overall path and the least cost AVB enabled path may be the same or may be different. Subsequent to step 310, the exemplary steps may advance to step 312. In step 312, a routing table and/or database may be populated based on the paths determined in step 308, and ports comprising the one or more nodes may be configured to implement the determined path(s).

FIG. 4 is a flow chart illustrating transmission of an AVB data stream utilizing AVB aware Shortest Path Bridging, in accordance with an embodiment of the invention. Referring to FIG. 4 the exemplary steps may begin with step 402 when a first node desires an AVB stream from a second node. Subsequent to step 402, the exemplary steps may advance to step 404. In step 404, the first node may refer to a routing table which identifies the least cost AVB enabled path or the AVB path which may provide the highest quality of service (QoS) between the first node and the second node. In this regard, the routing table may be populated utilizing steps such as the step 302 to 312 described in FIG. 3. Subsequent to step 404, the exemplary steps may advance to step 406. In step 406, the first node may attempt to reserve resources for the AVB stream along the path identified in step 406. Subsequent to step 408, the exemplary steps may advance to step 410. In step 410, it may be determined whether resources for the AVB stream have been successfully reserved across the least cost AVB enabled path. If the resources have been successfully reserved, then the exemplary steps may advance to step 416. In step 416, transmission of the AVB stream from the second node to the first node over the least cost AVB enabled path may begin.

Returning to step 410, if resources are unable to be reserved over the least cost AVB enabled path, the exemplary steps may advance to step 412. In step 412 it may be determined whether an alternative AVB enabled path is available. In this regard, a routing table or database, similar to the one populated in FIG. 3, may be accessed to determine if an alternate AVB enabled path exists. If an alternate path is available then the exemplary steps may advance to the previously described step 406. Accordingly, resources available in a path may be factored into the cost of the path, and a least cost AVB enabled path, with available resources, may determined.

Returning to step 412, if no alternate AVB enabled path exists, then the exemplary steps may advance to step 418. In step 418, the AVB stream may be denied and the first node may be notified that resources are unavailable. Alternatively, the first node may be given the option to accept lower quality stream, in which case resources may be available for lesser bandwidth or a non-AVB path may be utilized.

Aspects of a method and system for Audio/Video Bridging aware shortest path bridging are provided. In this regard, network nodes which are AVB enabled and capable of routing information based on a desired path cost and/or a desired quality of service (QoS), such as the nodes 208 in FIG. 2 may be identified. Furthermore, an AVB enabled path, such as the path 204, comprising one or more of the identified nodes may be established for communication over a network. In this regard, the desired cost may be a least cost, such as the optimum path described in FIG. 1B. Additionally, the nodes may be identified using Shortest Path Bridging protocols and/or Audio Video Bridging protocols and/or extensions thereof. Also, bridge protocol data units may be exchanged to identify the nodes, and may comprise one or more bits capable of identifying nodes which are AVB enabled and capable of routing information based on a desired path cost and/or quality of service. Aspects of the invention may enable network nodes to determine the availability of resources which may be reserved in one or more other nodes. Also, network traffic handled by one or more nodes which are AVB enabled and capable of routing information based on a desired path cost and/or a desired (QoS) may be monitored to enable identifying other nodes which are AVB enabled and capable of routing information based on a desired path cost and/or a desired (QoS). In this regard, SRP registration and or SRP reservation packets may be monitored to identify nodes which are AVB enabled and capable of routing information based on a desired path cost and/or a desired (QoS). Additionally, aspects of the invention may enable storage of a table, database, or other data structure which may enable indicating which nodes in a network may be AVB enabled.

Another embodiment of the invention may provide a machine-readable storage, having stored thereon, a computer program having at least one code section executable by a machine, thereby causing the machine to perform the steps as described herein for Audio/Video Bridging Aware shortest path bridging.

Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.

While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims. 

1. A method for providing communication in a network, the method comprising: identifying nodes in the network that are AVB enabled and capable of providing routing based on a desired cost and/or desired QoS; and establishing an AVB enabled communication path between a first endpoint and a second endpoint via one or more of said identified nodes to enable communication between said first endpoint and said second endpoint.
 2. The method according to claim 1, wherein said desired cost is a least cost.
 3. The method according to claim 1, comprising identifying nodes in the network based at least on shortest path bridging protocols.
 4. The method according to claim 1, comprising identifying nodes in the network based at least on Audio Video Bridging protocols.
 5. The method according to claim 1, comprising exchanging bridge protocol data units for said identifying of said nodes in the network.
 6. The method according to claim 5, wherein said bridge protocol data units comprise one or more bits that indicate audio/video bridging capability of said nodes in the network.
 7. The method according to claim 1, comprising determining availability of resources for reservation for each of said nodes in the network.
 8. The method according to claim 1, comprising monitoring traffic handled by at least a portion of said nodes in the network for said identification of said nodes in the network that are AVB enabled.
 9. The method according to claim 1, comprising monitoring SRP registration and/or SRP reservation packets for said identification of said nodes in the network that are AVB enabled.
 10. The method according to claim 1, comprising storing in one or more said nodes in the network, an indication of which nodes in the network are AVB enabled.
 11. A machine-readable storage having stored thereon, a computer program having at least one code section for providing communication in a network, the at least one code section being executable by a machine for causing the machine to perform steps comprising: identifying nodes in the network that are AVB enabled and capable of providing routing based on a desired cost and/or desired QoS; and establishing an AVB enabled communication path between a first endpoint and a second endpoint via one or more of said identified nodes to enable communication between said first endpoint and said second endpoint.
 12. The machine-readable storage according to claim 11, wherein said desired cost is a least cost.
 13. The machine-readable storage according to claim 11, wherein said at least one code section enables identifying nodes in the network based at least on shortest path bridging protocols.
 14. The machine-readable storage according to claim 11, wherein said at least one code section enables identifying nodes in the network based at least on Audio Video Bridging protocols.
 15. The machine-readable storage according to claim 11, wherein said at least one code section enables exchanging bridge protocol data units for said identifying of said nodes in the network.
 16. The machine-readable storage according to claim 15, wherein said bridge protocol data units comprise one or more bits that indicate audio/video bridging capability of said nodes in the network.
 17. The machine-readable storage according to claim 11, wherein said at least one code section enables determining availability of resources for reservation for each of said nodes in the network.
 18. The machine-readable storage according to claim 11, wherein said at least one code section enables monitoring traffic handled by at least a portion of said nodes in the network for said identification of said nodes in the network that are AVB enabled.
 19. The machine-readable storage according to claim 11, wherein said at least one code section enables monitoring SRP registration and/or SRP reservation packets for said identification of said nodes in the network that are AVB enabled.
 20. The machine-readable storage according to claim 11, wherein said at least one code section enables storing, in one or more of said nodes in the network, an indication of which nodes in the network are AVB enabled.
 21. A system for providing communication in a network, the system comprising: at least one processor that enables identification of nodes in the network that are AVB enabled and capable of providing routing based on a desired cost and/or desired QoS; and said at least one processor enables establishment of an AVB enabled communication path between a first endpoint and a second endpoint via one or more of said identified nodes to enable communication between said first endpoint and said second endpoint.
 22. The system according to claim 21, wherein said desired cost is a least cost.
 23. The system according to claim 21, wherein said at least one processor enables identification of nodes in the network based at least on shortest path bridging protocols.
 24. The system according to claim 21, wherein said at least one processor enables identification of nodes in the network based at least on Audio Video Bridging protocols.
 25. The system according to claim 21, wherein said at least one processor enables exchanging of bridge protocol data units for said identification of said nodes in the network.
 26. The system according to claim 25, wherein said bridge protocol data units comprise one or more bits that indicate audio/video bridging capability of said nodes in the network.
 27. The system according to claim 21, wherein said at least one processor determines availability of resources for reservation for each of said nodes in the network.
 28. The system according to claim 21, wherein said at least one processor monitors traffic handled by at least a portion of said nodes in the network for said identification of said nodes in the network that are AVB enabled.
 29. The system according to claim 21, wherein said at least one processor monitors SRP registration and/or SRP reservation packets for said identification of said nodes in the network that are AVB enabled.
 30. The system according to claim 21, wherein said at least one processor enables storage, in one or more of said nodes in the network, of an indication which specifies which nodes in the network are AVB enabled. 